pp108 : Setting the Global Configuration Properties

Setting the Global Configuration Properties
This topic describes the procedure to set the global configuration properties for installing ActiveMQ.

After installing ActiveMQ, modify the following properties to set up a suitable environment for configuring JMS and ActiveMQ:

  1. Create the file <CORDYSHOME>/config/reliableMessaging.properties and include the below properties: 
    # JMS JNDI properties file
java.naming.factory.initial=com.eibus.transport.jms.activemq.ActiveMQInitialContextFactory
java.naming.provider.url=failover:(tcp://localhost:61616)?initialReconnectDelay=100
queueconnectionfactory=QueueConnectionFactory
java.naming.security.authentication=none
#java.naming.security.principal
#java.naming.security.credentials
  2. Include Transaction Manager and the configuration file in wcp.properties. 
    com.cordys.xatransaction.TransactionManagerFactory=com.cordys.xatransaction.atomikos.AtomikosTransactionManagerFactory
com.cordys.transport.jms.jndifile=<CORDYSHOME>/config/reliableMessaging.properties
  3. To enable logging for Atomikos, modify Log4jConfiguration.xml in the <CORDYSHOME>/config: 
    <category name="com.atomikos">
    <priority value="debug"/>
    <appender-ref ref="OSBasedEventAppender"/>
</category>

The Transaction logging is included in the standard log files of Process Platform directory and in the service container log file.

Note: An additional directory that contains a binary log file with the post-fix #atomikos is created. For example, when a connection point is set for the BPM processor, there are two log entries:
system#business_process_management#business_process_management.xml: The standard log file that contains the logging details of Atomikos
system#business_process_management#business_process_management.xml#atomikos: The directory that contains the binary log file. Usually, this log file is not viewed or used because all the relevant messages are logged in the standard log file.